Skip to content

chore(deps): bump @openclaw/zalouser from 2026.10.9 to 2026.11.1 in /plugins/zalouser - #767

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/plugins/zalouser/openclaw/zalouser-2026.11.1
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/plugins/zalouser/openclaw/zalouser-2026.11.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 8, 2026

Copy link
Copy Markdown
Contributor

Bumps @openclaw/zalouser from 2026.10.9 to 2026.11.1.

Release notes

Sourced from @​openclaw/zalouser's releases.

openclaw 2026.11.1

2026.11.1

Highlights

Changes

  • Claude CLI: saved subscription accounts can make configured models available without a separate native login, and operators can opt into native Agent and Workflow orchestration through plugins.entries.anthropic.config.managedNativeTools; the default remains off and restricted runs keep their existing tool limits. (#179203, #183765) Thanks @​RomneyDa.
  • Anthropic: API-key setup can record an optional Anthropic workspace ID; existing workspace headers are preserved, and workspace-scoped keys need no extra setting. (#186976) Thanks Ayaan Zaidi, @​evomach, @​sukhdeepjohar, @​RomneyDa.
  • Google: Interactions requests honor managed proxy and TLS settings, rotate eligible API keys before streaming after a rate limit, preserve native video input, and forward nucleus sampling consistently; choose google-generative-ai when explicit Gemini cache handles are required. (#189395, #190695) Thanks @​RomneyDa.
  • Bedrock Mantle: discovered numbered OpenAI GPT models select the Responses route automatically, while GPT-OSS keeps Chat Completions and Claude keeps Anthropic Messages. Thanks @​MertBasar0, @​anmol0b, @​shakkernerd, @​kybrcore, @​sukhdeepjohar, @​potoior, @​RomneyDa.
  • Control UI: the model picker shows the configured active context budget rather than only the model maximum, and short session links retain their intended navigation target. (#180870, #183148) Thanks @​RomneyDa.
  • Google Chat: remote HTTP(S) attachments are delivered as visible links alongside captions; local files and native uploads remain unsupported with service-account authentication. Thanks @​RomneyDa.
  • Update diagnostics: detailed readiness separates a ready core from channel outages, allowing repaired updaters to finish with named channel warnings without hiding HTTP 503 or weakening normal service-start checks. Thanks @​duyufansh2008, @​RomneyDa.

Fixes

  • Network and tool safety: ClickClack and ClawHub reject redirects into unrelated private services, Discord CDN downloads no longer inherit browser private-network access, and FIFO native-hook credentials are rejected without hanging the agent. (#190944, #190939, #191458, #191423) Thanks @​pgondhi987, @​SebTardif, and @​Leon-SK668.
  • Doctor consent and access policy: noninteractive checks no longer download plugins without repair consent, and explicitly empty group allowlists remain empty instead of being repopulated. (#191523, #174787) Fixes #191420, #173826 Thanks @​brandonulrich, @​steipete, and @​lockhartheavyindustries.
  • Recovery data: malformed UTF-8 legacy imports are rejected instead of replacing original content; failed skill restore rollbacks preserve the original copy, and cleanup refuses destructive work when workspace inspection fails. (#180861, #173954, #174195, #176362) Fixes #180782, #180795 Thanks @​RomneyDa, @​duyufansh2008, @​steipete, and @​wangmiao0668000666.
  • Log redaction: malformed custom entries no longer disable valid rules or built-in secret protection; invalid policy is reported while safe redaction remains active. (#173471) Thanks @​skyzhao1223 and @​RomneyDa.
  • Secret egress: reject chains relying on the distrusted emSign ECC G3 root in the managed proxy and exported subprocess CA bundle; restart the Gateway after updating, and update clients with independent trust stores separately. (#179249) Thanks @​RomneyDa.
  • macOS connectivity: configured credentials take precedence over stale app environment, typed environment secret references resolve correctly, and remote Settings respects the Control UI base path. (#191468, #185141, #128175) Fixes #164596 Thanks @​RomneyDa, @​anmol0b, and @​goldmar.
  • Mac tools and messaging: iMessage remains usable after app updates without re-granting Automation, Peekaboo window inspection accepts valid snapshot references, and node exec preserves results for commands configured without a timeout. (#186107, #172116, #190729) Fixes #178719 Thanks @​aniketkrs, @​RomneyDa, @​anmol0b, @​SharkeyDev, @​holgergruenhagen, @​LiuwqGit, and @​etzelm.
  • Mac voice and embedded pages: avoid duplicate voice sends and false sent feedback, and show a recoverable load error instead of a blank or stale Mac tab. (#186271, #185432) Thanks @​anmol0b, @​etzelm, and @​RomneyDa.
  • Native voice and capture: iOS and macOS Talk tolerate slow audio acknowledgments within bounded buffering, long meeting replies are not cut off merely because generation outruns playback, and oversized Mac recordings fail with size guidance instead of dropping the node connection. Thanks @​MertBasar0, @​anmol0b, @​shakkernerd, @​kybrcore, @​sukhdeepjohar, @​potoior, and @​RomneyDa.
  • Android and desktop compatibility: Android Chat waits for the role-allowed agent list after switching Gateways, and independently updated Mac nodes can return optional cursor coordinates without a computer-use contract error. Thanks @​MertBasar0, @​anmol0b, @​shakkernerd, @​kybrcore, @​sukhdeepjohar, @​potoior, @​RomneyDa.
  • Channel recovery: Slack detects dead relay connections without treating ordinary silence as failure, Tlon reconnects stalled streams so unacknowledged events can replay, and managed Tailscale exposure recovers after a daemon restart while local authenticated access stays available. Thanks @​RomneyDa.
  • Channel delivery: Feishu keeps text from before and after tool calls in the same streaming card; Synology confirms delivery only from recipient-matched message IDs; Twitch targets and Zalo unsupported-event text follow their channel handling rather than silently losing usable content. Thanks @​RomneyDa.
  • Channel credentials and notices: implicit Slack default accounts retain complete top-level credentials alongside named accounts, channel secret consumers respect account activation, and Nostr reports failed pairing notifications without undoing approval. Thanks @​RomneyDa.
  • iMessage storage: recovery cursor keys no longer contain a PostgreSQL-incompatible NUL separator, allowing the channel to start with PostgreSQL-backed state. (#184919) Fixes #184862 Thanks @​duyufansh2008, @​RomneyDa, and @​etzelm.
  • Session and agent authority: deleting one agent no longer breaks other agents' tool authority, and local session-capability changes stop inappropriate provider fallback instead of trying every model. (#174918, #179312) Fixes #179290 Thanks @​steipete, @​chelsealong, @​obviyus, and @​Marvinthebored.
  • Prompt caching: session tool definitions stay stable across turns, including completions, heartbeats, and non-owner requests, avoiding unnecessary prompt-cache misses. (#175309, #176167) Thanks @​obviyus.
  • Conversation recovery: compaction retains the active human request across repeated summaries; queue overflow summaries retain each visible sender and conversation context; exec completion guidance survives overflow. (#180214, #187833, #190698, #182188, #184216) Thanks @​RomneyDa and @​aniketkrs.
  • Codex continuity: conversation-wide restrictions retain compatible native threads, temporary restrictions preserve the ordinary conversation binding, and a missing thread with recorded history reports an error instead of silently starting over. Thanks @​skyzhao1223 and @​RomneyDa.
  • Codex replies: transient retries can summarize the original request and completed tools without rerunning them; terminal handoffs allow already-submitted steering a bounded chance to confirm consumption and do not automatically replay uncertain input. (#183077, #184062, #181839, #167390) Thanks @​RomneyDa.
  • Shared credentials and model availability: concurrent MCP callers can reuse a fresh OAuth token without unnecessary exclusive locking, rate-limit cooldowns follow provider timing instead of accumulating hours of local backoff, and fresh model publications replace superseded refresh results. (#179997, #180280, #179144) Thanks @​RomneyDa.
  • Claude CLI and scheduled work: canceled cron runs stop reply hooks, interrupted long-running jobs no longer prevent scheduler startup, oversized or invalid CLI streams cancel their subprocess promptly, and managed completions retain the policy-filtered tool catalog. (#181245, #191422, #159931, #172026) Thanks @​steipete and @​fuller-stack-dev.
  • Session history and memory: long transcript decoding releases database read snapshots promptly, bounded history pages keep their requested anchors and adjacent messages, and memory indexing waits for archived transcript materialization. (#164442, #172970, #177937, #182091, #190182, #189284, #188450, #188483, #190690) Fixes #171467 Thanks @​RomneyDa, and @​etzelm.
  • Subagent and restart recovery: live descendants keep their expired parents available for communication, accepted yields settle sibling tool results before handoff, and stale interrupted input no longer blocks a new human message indefinitely. (#179057, #184021, #180853, #181871, #178888, #184041, #184069, #172959) Thanks @​RomneyDa.
  • Agent handoffs: waiting session sends recover the stored long reply instead of returning only a short lifecycle preview, and ACP-created sessions retain the requested working directory for later prompts. (#178271, #176852) Thanks @​RomneyDa.
  • Control UI recovery: silently dead Gateway connections reconnect without replaying uncertain sends, consumed slash-steering messages leave the queue, and routine restart notices stay concise. (#179101, #178642, #180024, #172843) Thanks @​RomneyDa.

... (truncated)

Changelog

Sourced from @​openclaw/zalouser's changelog.

Changelog

Release notes: https://docs.openclaw.ai/releases

Each release has its complete changelog below. Audited contribution records are retained separately when available.

... (truncated)

Commits
  • 4ffdd20 test(release): supply the state script to manifest writer proofs
  • d285b6a ci(release): route FRV state operations to admitted tooling
  • b8fbe16 test: widen hosted cold-start limits for durability and voice-call proofs
  • ec5d8d2 test(workers): format the aged memo clock import
  • 3a4983e fix(test): report HTTP status when cache probes fail
  • c16f7a9 test(workers): age fixture ctimes for memo reuse proofs
  • ef14ea4 chore(release): attest 2026.11.1 candidate
  • 5a44cd1 fix(release): shorten branch push preflight (#188743)
  • adbc189 refactor: split oversized backport modules
  • ea0a7c8 fix(agents): honor user constraints during response recovery
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@openclaw/zalouser](https://github.com/openclaw/openclaw) from 2026.10.9 to 2026.11.1.
- [Release notes](https://github.com/openclaw/openclaw/releases)
- [Changelog](https://github.com/openclaw/openclaw/blob/main/CHANGELOG.md)
- [Commits](openclaw/openclaw@v2026.10.9...v2026.11.1)

---
updated-dependencies:
- dependency-name: "@openclaw/zalouser"
  dependency-version: 2026.11.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 8, 2026
@clawsweeper

clawsweeper Bot commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

@clawsweeper clawsweeper Bot added P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. merge-risk: 🚨 security-boundary 🚨 Merging this PR could weaken sandboxing, authorization, credentials, or sensitive data. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. labels Nov 8, 2026
@clawsweeper

clawsweeper Bot commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

Codex review: needs real behavior proof before merge.

What this changes

Updates the Zalo Personal fixture fallback to @openclaw/zalouser 2026.11.1 and refreshes its lockfile metadata.

Example: The configured Zalo Personal npm tag is unavailable.

  • Before: Crabpot falls back to 2026.10.9.
  • After: Crabpot falls back to 2026.11.1.

Review scores

Measure Result What it means
Overall readiness 🧂 unranked krab (1/6) Useful maintenance with a definite attribution defect and unresolved credential-authority and upgrade qualification.
Proof confidence 🧂 unranked krab (1/6) Real behavior proof is necessary before merge. See Before merge.
Patch quality 🦐 gold shrimp (3/6) Security review found an item that needs attention.

Product

Kind: Maintenance · Worth it: Yes · Fix scope: Complete
User problem: The frozen fallback fixture does not cover the newly published Zalo Personal package and its changed runtime contracts.
Reason: Maintaining representative published fallbacks has merged precedent, and this archive contains substantive credential and migration changes.

Merge readiness

⛔ Blocked before merge - 6 items remain

Keep this PR open: main still uses 2026.10.9, and the update would attribute the new fallback artifact to the previous release’s source.

Priority: P3
Reviewed head: 062d3f998460e05a76c1f7ef22f50ecee2c9e89b

Before merge

  • Add real behavior proof - Authority-chain proof required: show the selected artifact’s QR-login credential owner accepting a current login and rejecting a superseded login before the final persisted write, including revocation during awaited work. This bot PR is outside the ordinary contributor proof gate; its compatibility job does not declare that scenario. Existing credentials and legacy DM sessions also need upgrade evidence for the changed Doctor paths. The CI artifact could not be downloaded through the environment allowlist, which is not a contributor defect; targeted redacted logs or terminal evidence would resolve the remaining scenario gaps. After adding proof, update the PR body, then request a new review with @clawsweeper re-review. The PR author or someone with repository write access can request it.
  • [P2] Update the paired source references with the fallback (P2) - When tag resolution falls back to 2026.11.1, neither its registry metadata nor its package supplies gitHead. readPackagePayloadSourceRef consequently passes the matching new payload and shim versions to packageEvidenceRef, which returns the unchanged manifest reference 8b18b5578f66eab1501cba4cef2310d88bfb9a41. Reports therefore link the new artifact to the preceding release’s source. Update crabpot.config.json’s source.ref and this shim’s crabpot.sourceRef together from verified prepared-artifact provenance, and refresh affected generated expectations as required by AGENTS.md.
  • Resolve security concern: Verify authority enforcement at credential persistence - The selected archive transfers assertCurrent from individual credential operations into openKeyedStoreV2 construction and removes older-store paths; no concrete bypass was established.
  • Resolve merge risk - The PR owner must establish that moving credential authority checks into store construction still rejects a superseded login before credential persistence.
  • Add data-model compatibility proof - The review found that existing stored data may not work after upgrade. Show that existing data still loads and works with this change.
  • Explain or restore the original intent of Fallback package and prepared-source pairing - aa34909: chore(deps): refresh 21 official plugin fallbacks to 2026.10.9 #653 paired the previous fallback with verified prepared-source provenance while preserving moving tracks and the separately qualified host.

Findings

  • [P2] [P2] Update the paired source references with the fallback — plugins/zalouser/package.json:7
  • [medium] Verify authority enforcement at credential persistence — plugins/zalouser/package.json:7

Provenance

Tests

  • Missing end-to-end proof: Supplied evidence does not establish authorized versus superseded credential writes or an upgrade preserving existing credentials and legacy DM sessions.
Agent review details

How this fits together

Crabpot materializes configured plugin packages, inspects their compatibility with an OpenClaw host, and generates reports with upstream source links.

flowchart LR
 A[Fixture manifest] --> C[Package materializer]
 B[Fallback pin and lock] --> C
 C --> D[Plugin payload]
 D --> E[Compatibility inspector]
 E --> F[Reports and source links]
Loading

Technical review

Best possible solution:

Pair the fallback with verified prepared-source references and qualify its credential and migration behavior while preserving existing track selectors and host ownership.

Do we have a high-confidence way to reproduce the issue?

The reporting defect follows directly from the verified archive lacking gitHead and the report owner selecting the old source reference when the payload matches the updated pin; no target code was executed.

Is this the best way to solve the issue?

Updating the existing fallback is appropriately scoped, but changing its version without its paired source references breaks the established attribution contract.

Full review comments:

  • [P2] [P2] Update the paired source references with the fallback — plugins/zalouser/package.json:7
    When tag resolution falls back to 2026.11.1, neither its registry metadata nor its package supplies gitHead. readPackagePayloadSourceRef consequently passes the matching new payload and shim versions to packageEvidenceRef, which returns the unchanged manifest reference 8b18b5578f66eab1501cba4cef2310d88bfb9a41. Reports therefore link the new artifact to the preceding release’s source. Update crabpot.config.json’s source.ref and this shim’s crabpot.sourceRef together from verified prepared-artifact provenance, and refresh affected generated expectations as required by AGENTS.md.
    Confidence: 0.99

Overall correctness: patch is incorrect
Overall confidence: 0.95

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 4907a46607cc.

Merge-risk options

Maintainer options:

  1. Qualify the changed credential boundary (recommended)
    The PR owner supplies final-write evidence for an authorized login and a superseded login using the selected artifact and its real storage owner.
  2. Defer the fallback update
    A maintainer retains the reviewed 2026.10.9 fallback until the changed boundary can be qualified.

Provenance checked

Testing

Proof path: in-process harness.

Security

Needs attention: Artifact integrity matches, but the changed credential-authority boundary needs final-write qualification.

Evidence

Security concerns:

  • [medium] Verify authority enforcement at credential persistence — plugins/zalouser/package.json:7
    The selected archive transfers assertCurrent from individual credential operations into openKeyedStoreV2 construction and removes older-store paths; no concrete bypass was established.
    Confidence: 0.91

What I checked:

  • Introduced change and current main: The pinned diff updates only the package and lockfile; main retains 2026.10.9, while the shim sourceRef and manifest source.ref remain 8b18b5578f66eab1501cba4cef2310d88bfb9a41. (plugins/zalouser/package.json:7, 062d3f998460)
  • Reachable attribution defect: readPackagePayloadSourceRef supplies the payload version, shim pin, and manifest source reference to packageEvidenceRef; matching versions without gitHead select the unchanged source reference. (scripts/report-lib.mjs:334, 4907a46607cc)
  • Established source-pairing contract: chore(deps): refresh 21 official plugin fallbacks to 2026.10.9 #653 deliberately paired the preceding fallback refresh with verified prepared-source references and distinguished exact fallback execution from moving-track qualification. (plugins/zalouser/package.json:15, aa349094d146)
  • Published artifact and dependency-policy boundary: Both npm archives were read without execution and matched their registry SHA-512 integrities; neither contains gitHead or package lifecycle scripts. Crabpot materializes and executes this dependency during qualification, establishing the dependency-contract signal. Complete root and extensions policies were read at publication revision 3816bcb3dea1879d055853fc070af78bc7737ab0; the npm attestation identifies https://github.com/openclaw/openclaw/actions/runs/41976097719. (extensions/AGENTS.md, 3816bcb3dea1)
  • Credential authority and migration changes: The selected archive moves credential-write guards into openKeyedStoreV2 construction and removes older-store paths; its Doctor artifact also changes persisted credential and legacy session migration behavior. These changes were independently inspected rather than inferred from release notes. (extensions/zalouser/src/session-state.ts, 3816bcb3dea1)
  • Supplied validation and its limits: The isolated Zalo Personal fixture and lock-security checks passed. The workflow exercises materialization and compatibility inspection but does not declare current-versus-superseded login persistence or an existing-state upgrade scenario. Its artifact download was blocked by the environment’s Azure-host allowlist; that infrastructure limit is not a contributor defect. (.github/workflows/check.yml:243, 062d3f998460)

Likely related people:

  • Peter Steinberger: Raw commit aa34909 adds plugins/zalouser/package.json:15 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: aa349094d146; files: plugins/zalouser/package.json)
  • Vincent Koc: Raw commit 614b320 adds plugins/zalouser/package.json:13 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: 614b3209ea42; files: plugins/zalouser/package.json)

Preflight source

Source unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified.

Root-cause cluster

Relationship: canonical
Canonical: #767
Summary: This PR replaces the preceding Dependabot update for the same fallback package.

Members:

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Labels

Label changes:

  • add P3: Routine fixture maintenance with a bounded reporting defect and no demonstrated urgent user regression.
  • add merge-risk: 🚨 security-boundary: The selected artifact changes how login authority guards persisted credentials, requiring evidence at the final write.
  • add rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🦐 gold shrimp.
  • add status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask.

Label justifications:

  • P3: Routine fixture maintenance with a bounded reporting defect and no demonstrated urgent user regression.
  • merge-risk: 🚨 security-boundary: The selected artifact changes how login authority guards persisted credentials, requiring evidence at the final write.
  • rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🦐 gold shrimp.
  • status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask.

Rank-up moves

Optional improvements that raise the rating; they are not merge blockers.

  • Add final-effect proof that a current login can persist credentials and a superseded or revoked login cannot write them after awaited work.

Rating scale

6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior.

Workflow

ClawSweeper edits this one comment on every review. Comment @clawsweeper re-review for a fresh review only. Repair and merge execution lanes are retired.

Reviewed November 8, 2026, 4:28 AM ET / 09:28 UTC.

@vincentkoc

Copy link
Copy Markdown
Member

Closing this @openclaw/zalouser@2026.11.1 update because it is incompatible with the currently qualified host.

The Default Track pin selects OpenClaw 5f84c5b8a9889ab7035c197bc25bbe0aa8a20765 (2026.10.6). This package declares native openclaw.compat.pluginApi: ">=2026.11.1"; the pinned host’s admission policy skips it. The optional npm peer does not waive that gate.

Reconsider after an eligible immutable host completes full-corpus and three-platform qualification, its source pin is promoted through review, and the exact package cohort is qualified. Tracked in #780. Publication provenance alone is not runtime compatibility evidence.

@vincentkoc vincentkoc closed this Nov 9, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 9, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/plugins/zalouser/openclaw/zalouser-2026.11.1 branch November 9, 2026 06:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code merge-risk: 🚨 security-boundary 🚨 Merging this PR could weaken sandboxing, authorization, credentials, or sensitive data. P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant